Release 10.1A: OpenEdge Development:
Web Services

Progress Explorer framework for configuration and deployment

Within OpenEdge, the WSA is encapsulated as a server that you manage using the Progress Explorer or the wsaman command-line utility (see the information on WSA configuration and Web service deployment components in OpenEdge Getting Started: Application and Integration Services ). While these utilities support most WSA configuration options, you must edit the local ubroker.properties file for your WSA installation by hand to set some WSA configuration properties, particularly those that define WSA administration roles and their associated access permissions. Similar to other OpenEdge servers, OpenEdge provides the wsaconfig command-line utility to validate manual changes to the ubroker.properties file for WSA configuration.

You can also use the Progress Explorer or wsaman to temporarily change a selected set of WSA instance properties at run time (WSA Run-time Properties). This can be helpful for debugging or testing certain settings before making them permanent in your WSA configuration.

You must also use Progress Explorer or wsaman to deploy Web services to a particular WSA instance and to manage deployed Web services at run time. Each deployed Web service behaves according to the settings of a predefined set of run-time properties. While these properties have maintainable default values initially set for all Web services deployed to a WSA instance, you can set and reset their values, under prescribed run-time conditions, for each Web service individually.

For more information on WSA configuration and administration and on deploying and configuring Web services, see OpenEdge Application Server: Administration .